| 1. | Table scans always read and lock all the rows in the table
表扫描总是读取（并上锁）表中所有行。 |
| 2. | Cumulative count of range and table scans started on the index or heap
从索引或堆开始的范围和表扫描的累积计数。 |
| 3. | However , if no indexes are available , the query optimizer must use a table scan
但如果没有索引，则查询优化器必须扫描表。 |
| 4. | A table scan generates many disk i o operations and can be resource intensive
扫描表会有许多磁盘i / o操作，并占用大量资源。 |
| 5. | It will choose indexed access if it has lower cost than table scan
如果使用索引的开销比表扫描的开销低，优化器将选择索引访问。 |
| 6. | Table scan behavior
表扫描行为 |
| 7. | The method may be a table scan , or may be scanning one or more indexes if they exist
可能采用的方法包括扫描表和扫描一个或多个索引（如果有） 。 |
| 8. | Avoid indexing very small tables because it is typically more efficient to do a table scan
因为进行表扫描通常效率更高，所以要避免对非常小的表创建索引。 |
| 9. | The optimizer is more likely to choose a full table scan over an index if the value of this parameter is high
为什么设置高了，优化器会选择全表扫描而不选择索引？ |
| 10. | This prevents a large table scan from completely dominating the buffer pool and adversely impacting random operations
这样可以防止大规模的表扫描完全支配缓冲池，并恶劣地影响随机操作。 |
